-
Notifications
You must be signed in to change notification settings - Fork 0
docs: Add fork branch strategy documentation #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Documents the two-branch model used in the Intercom fork: - main: Clean upstream mirror (auto-synced weekly) - fork-main: Active development with pending upstream contributions Explains the fast-track workflow for using features before upstream acceptance while maintaining automated sync capabilities.
|
|
||
| ### `main` - Upstream Mirror | ||
| - **Purpose**: Clean mirror of the upstream `open-telemetry/opentelemetry-ruby-contrib` main branch | ||
| - **Updates**: Automatically synced weekly via GitHub Actions ([workflow](https://github.com/intercom/intercom/blob/master/.github/workflows/sync-org-forks.yml)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [linkspector] reported by reviewdog 🐶
Cannot reach https://github.com/intercom/intercom/blob/master/.github/workflows/sync-org-forks.yml Status: 404
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was expected! 😁
|
|
||
| ## Questions? | ||
|
|
||
| For questions about this fork or the branch strategy, ask in #builder-tools or consult the [sync workflow documentation](https://github.com/intercom/intercom/blob/master/.github/workflows/sync-org-forks.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚫 [linkspector] reported by reviewdog 🐶
Cannot reach https://github.com/intercom/intercom/blob/master/.github/workflows/sync-org-forks.md Status: 404
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was expected! 😁
Adds a pull request template that reminds developers to target fork-main instead of main. The template includes: - Clear warning about base branch selection - Explanation of branch purposes (fork-main vs main) - Standard PR sections (Why, How, Test Plan) - Link to FORK.md documentation This helps prevent accidentally creating PRs against the locked main branch which is reserved for automated upstream syncing.
The PR template was starting with a level 2 heading (##), which violated markdown lint rules requiring the first heading to be level 1 (#). This change updates the first heading to use the correct level 1 format.
Why?
The Intercom fork uses a two-branch model that needs documentation so team members understand:
fork-main)mainbranch)Without this documentation, it's unclear why we have two branches and how to work with them.
How?
Created
FORK.mdthat documents:main(upstream mirror, auto-synced) vsfork-main(active development)The documentation follows the established pattern from the Intercom monolith's sync workflow and provides practical commands for common operations.